-
Notifications
You must be signed in to change notification settings - Fork 747
refactor(amazonq): Improve robustness of lsp installation process #6364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(amazonq): Improve robustness of lsp installation process #6364
Conversation
|
|
/runIntegrationTests |
packages/amazonq/src/lsp/client.ts
Outdated
| } | ||
|
|
||
| const child = cp.spawn('node', [serverPath, ...debugOptions.execArgv]) | ||
| const child = cp.spawn(executablePaths.node, [serverPath, ...debugOptions.execArgv]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we can find a way to use our ChildProcess module, then after #6304 we get instrumentation for free :)
| ).resolve() | ||
|
|
||
| const nodeName = | ||
| process.platform === 'win32' ? getNodeExecutableName() : `node-${process.platform}-${process.arch}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would the node-platfor-arch logic fit into getNodeExecutableName ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason this idea only exists for the workspace installer. I think the actual standard (which the actual codewhisperer language server uses) is just node.exe/node
Problem
Solution
feature/xbranches will not be squash-merged at release time.